Structure for an integrated circuit design for reducing coupling between wires of an electronic circuit

ABSTRACT

A design structure for reducing coupling between wires of an electronic circuit is proposed, wherein sets of nets are classified according to their coupling characteristics, and spacing between wires assigned to the sets of nets is chosen according to the coupling characteristics.

CROSS REFERENCES TO RELATED APPLICATIONS

This application is a continuation-in-part of presently U.S. application Ser. No. 11/845,301, entitled “ROUTING METHOD FOR REDUCING COUPLING BETWEEN WIRES OF AN ELECTRONIC CIRCUIT”, filed on Aug. 27, 2007 now abandoned, which is fully incorporated herein by reference.

This application is related to German Patent Application No. 06124167.5, filed Nov. 15, 2006.

FIELD OF THE INVENTION

The present invention relates to a design structure for reducing coupling between wires of an electronic circuit. In particular, the present invention relates to a design structure for reducing coupling between wires of an electronic circuit, wherein sets of nets are classified according to their coupling characteristics, and spacing between wires assigned to the sets of nets is chosen according to the coupling characteristics.

BACKGROUND OF THE INVENTION

There are many steps and processes involved producing microelectronic components such as computer processing units (CPUs) and application specific integrated circuits (ASICs), which are widely used in computers, cell phones, and portable electronics. Making electronics smaller and smaller raises new challenges in manufacturing CPUs and ASICs. Physical properties of the materials in semiconductor devices that previously did not affect the manufacturability or performance have become a major deterrent.

Designing modern electrical circuits such as CPUs and ASICs with wire dimensions of 130 nm and below has become increasingly difficult due to shrinking distance rules (“wire pitch”) which cause capacitive coupling between proximate wires. Coupling describes an electromagnetic effect where a signal change in one wire (aggressor wire) can affect the signal in a proximate wire (victim wire). The aggressor wire can either cause the victim wire to change its static value for a certain time span, a so called “glitch”, or it can cause a signal change in the victim wire to either speed up or slow down. In any case this can cause a digital system to fail because wrong signal values may be propagated.

Several approaches are known for eliminating the capacitive coupling between aggressor wires and victim wires.

The simplest approach to reduce coupling problems known in the art involves proceeding with standard routing and then fixing the problems with a post process, either manually or automatically. The standard routing would be done after timing closure based on the so called Steiner routes. Afterwards, the designer would do coupling analysis. Based on the analysis to avoid coupling problems logic changes are made by inserting repeaters or resized drivers in victim nets (the data representation of a wire in the design tools chain) and victim wires and optionally aggressor wires are rerouted with extra space using an isolated wire type.

The drawbacks are that the logic changes require the design infrastructure to support the ability to modify cells on routed designs. In the worst case, there is no solution, because adding additional buffers to timing critical nets can add too much delay or large enough drivers may not exist. Adding extra space consumes a lot of wiring resources and can have the side effect of causing detours, opens, or unwirability. If the extra space were a soft requirement, perhaps no detours or opens would be generated. However, the original issues would not be solved, especially in congested regions where coupling issues are most likely to occur.

Another approach, for example, involves routing all nets with a recommended extra space. As in the approach described above, a post processing is still required.

An automated method for analyzing crosstalk between wires is disclosed in the U.S. Pat. No. 6,507,935 B1. For at least one potential victim wire of a plurality of wires, a subset of the wires of the chip are found to be potential aggressor wires to the victim wire. An alarm threshold for each potential victim wire is determined and is compared to a calculated height of a coupled noise on the victim wire to determine which wires of the design suffer enough crosstalk noise that they should be redesigned. A similar approach is disclosed in the U.S. Pat. No. 6,327,542 B1, which proposes a method for determining an aggressor coupling capacitance and the coupling voltage noise. Both disclosures, however, suggest analyzing the crosstalk between the wires of a net. A post processing of the net is necessary, if the crosstalk level is too high.

A method for avoiding crosstalk between wires is disclosed in the U.S. Pat. No. 6,510,545 B1. Reducing the crosstalk is accomplished by introducing VDD and VSS wires proximate to signal wires on the same metal layer which reduce the crosstalk by shielding the signal wires. Such shields are implemented on all the wires of the net. Shields are deleted in areas where they are considered to be unnecessary. Although an efficient method to avoid crosstalk is suggested, the method is expensive and can practically only be applied to a small number of nets.

It is therefore an object of the invention to provide an improved integrated circuit design which allows for reducing coupling between wires in electronic circuits in a cost efficient way, thus avoiding unnecessary post processing, and corresponding computer programs, computer program products and computer systems.

The objects of the invention are achieved by the features of the independent claims. The other claims and the description disclose advantageous embodiments of the invention.

SUMMARY OF THE INVENTION

According to the invention, a design structure for reducing coupling between wires of an electronic circuit is proposed, wherein sets of nets are classified according to their coupling characteristics, and spacing between wires assigned to the sets of nets is chosen according to the coupling characteristics.

Advantageously, capacitive coupling between the wires in electronic circuits can be reduced substantially or even be eliminated while preserving as many wiring resources as possible. The method requires only few routing resources, less than the known approaches. Wire spacing is required only when necessary. By isolating victim wires from all their aggressors, a root problem of coupling issues is solved. Signal nets can be placed adjacent to other “safe” nets. Default nets can be next to all other nets, victim nets can be next to other victim nets and aggressor nets can be next to other aggressor nets.

A user can update the technology files, usually used in design and/or routing, that define wire spacing requirements without the need of introducing any changes to the router source algorithms or source code. As such, this is runtime efficient: no on-the-fly checks are required, since coupling avoidance is defined in the technology rules. Such technology files serve as special input for routing programs. The technology files provide concrete design rules for each concrete (hardware) implementation process, for example various CMOS (Complementary Metal Oxide Semiconductor) technologies. The technology files are necessary for generic routing programs to be able to support the specific process.

The invention can be combined with other existing approaches for reducing the coupling. Most if not all routers optimize their capability to deal with new wire types or spacing rules to anticipate new technologies and changing customer and manufacturing requirements. The effectiveness of the capacitive coupling reduction can be measured by the amount of coupling parasitics present on the wire signals before and after the special wire types with customized spacing rules have been applied.

Preferably, the electronic circuit is adopted in an electronic device, such as a CPU or an ASIC or a printed circuit board. Most preferred is the electronic device based on a sub-micron technology with a wire pitch of at most ca. 400 nm.

According to a preferred embodiment, at least one set of nets is classified as a victim set, which contains nets, preferably all nets, that are classified victims to one or more coupling issues, and at least one set of nets as an aggressor set, which contains nets, preferably all nets, that are classified aggressors of one or more coupling issues, and specific distance rules are applied to the different sets of nets.

Reasonably, at least one victim-aggressor set, which contains nets, preferably all nets, that are classified victims and aggressors of one or more coupling issues, and/or a default set, which contain nets, preferably all nets, which are insensitive to coupling issues, are introduced additionally.

For implementation of the sets of nets in a lay-out of the electronic circuit, wire types are assigned to a specific set of nets. Preferably, the wires are arranged two-dimensionally in multiple layers.

Favorably, spacing between proximate wires is chosen depending on their specific wire types. Additional spacing is only provided if necessary.

Preferably, a first distance rule between a first wire and a second wire is applied, which second wire is proximate to the first wire unless:

-   -   the first wire is a victim wire and the second wire is an         aggressor wire or a victim-aggressor wire, or     -   the first wire is an aggressor wire and the second wire is a         victim wire or a victim-aggressor wire, or     -   the first wire is a victim-aggressor wire and the second wire is         a victim wire or an aggressor wire or a victim-aggressor wire;         where for these cases a second distance rule is applied.

Spacing between proximate wires is preferably increased to avoid coupling. Reasonably, the spacing is increased if one of two or both proximate wires cause coupling in its neighbor.

Another preferred embodiment is preferably applied if the router program in use is not restricted to supporting only spacing based on wire widths. In practice, in a typical design 99% of the wires are of equal width. The IC design described also works with wires of varying widths.

In this embodiment, minimum space consumption can be achieved if with the first distance rule a minimum space is chosen as a first spacing. This space is preferably equal to the minimum space requirement for the specific manufacture technology which will be employed for the manufacture of the electronic circuit.

With the second distance rule an extra space is added to the first spacing yielding a second spacing. Additional space is only provided where necessary. Wires of “safe” wire types, which do not cause coupling issues, can be arranged next to each other.

According to another preferred embodiment, wire widths are assigned to at least two wire types. Preferably all wire types differ in their respective widths, wherein the widths are representative for each specific wire type. This is preferably applied if the router program supports only spacing based on wire widths.

Preferably, the widths increase in the same order of default wire types, victim wire types, aggressor wire types, victim-aggressor wire types as a spacing requirement decreases between wires of the same type, yielding a constant wire pitch for routing for each net. The default widths and default spacings can be specific for each net. In practice, default widths as well as default spacings of different nets usually are the same for the majority of nets.

The wire widths can preferably increase by an even-numbered multiple of a router resolution. Reasonably, the resolution is much smaller than a default width applied to the wires. For routing purposes, one specific wire type can be reliably distinguished from the other wire types by a slight difference in its wire width compared to the other wire widths.

Preferably a spacing between wires decreases from default wire to victim wire to aggressor wire to victim-aggressor wire types, if the first wire is of default wire type.

For example, the wire widths can increase from default wire to victim wire to aggressor wire to victim-aggressor wire types whereas the spacing requirement between wires of the same wire type decreases from default to victim to aggressor to victim-aggressor wire types, where favorably the spacing requirement decreases by an even-numbered multiple of a router resolution.

With the first distance rule, wire spacing is decreasing in units of the router resolution. The spacing between proximate default wires is preferably the default spacing resulting from the technology used for manufacturing the respective electronic circuit.

With the second distance rule, an additional spacing is added to the first wire spacing.

Additional types of victim and aggressor nets can be included. The distance and/or wire widths rules can be adapted to save additional wiring resources.

To avoid detours on important signals, it is possible to apply a weighing function to at least one timing critical net in all proposed embodiments. As timing is important for the performance of the electronic circuit, this allows prioritizing the net or nets which are critical for the timing.

Most preferably, routing is performed with the steps of

-   -   defining sets of nets of different kinds, especially default         nets, victim nets, aggressor nets and victim aggressor nets,     -   perform global routing of the electronic circuit,     -   run a coupling analysis,     -   assign wire types to the kinds of nets, especially assign         default wire types to default nets, victim wire types to victim         nets, aggressor wire types to aggressor nets and         victim-aggressor wire types to victim-aggressor nets,     -   perform local routing,     -   run a coupling analysis based on the local routing results,     -   assign wire types to the kinds of nets,     -   rip-up and reroute new wire types, allowing rip-up of others,     -   repeat routing and assigning steps if necessary,     -   reset wire widths to original widths, if wire widths have been         changed for routing,     -   return from routing.

This makes sure that at least for mask generation after the routing process the wire widths are reset to their original values.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention together with the above-mentioned and other objects and advantages may best be understood from the following detailed description of the embodiments, but not restricted to the embodiments, wherein is shown in:

FIG. 1 illustrates a coupling issue between an aggressor wire and a victim wire;

FIG. 2 a-b illustrate default widths and default spacings (a) and spacings where a distance rule has been applied (b) according to a first embodiment of the invention;

FIG. 3 illustrates a table indicating distance rules for wire types according to a first embodiment of the invention; and

FIG. 4 illustrates a table indicating distance rules for wire types according to a second embodiment of the invention.

FIG. 5 illustrates a flow diagram of a design process used in semiconductor design, manufacturing, and/or test.

DETAILED DESCRIPTION

FIG. 1 schematically depicts a coupling issue between an aggressor wire A and a victim wire V. A capacitive coupling issue between the two wires A and V is indicated by a capacitor C.

A step like signal is applied to the aggressor wire A as indicated on the left side of the figure. The signal couples into the victim wire V yielding a pulse signal which falsifies the state of the victim wire V.

As depicted in the FIGS. 2 a and 2 b, a default wire D is assigned a default width w_default and a default spacing s_default to a proximate default wire D (FIG. 2 a). The width and the spacing typically are a result of the actual technology files applied for a certain electronic circuit under development. As known in the art, those technology files typically comprise requirements for minimum wire widths, minimum spacings and other parameters which may be influenced by deposition and/or etching techniques, mask design, the specific layer of the wiring etc., which are applied in the fabrication technology of the device.

FIG. 2 b depicts an aggressor wire A proximate to a victim wire V, where an additional spacing e has been introduced between the two wires to increase their distance and to reduce the coupling from the aggressor wire A to the victim wire V, where, for example, the new spacing is s_default+e. Reasonably, e can be of the same size as the width and/or the spacing. For example, for a CMOS 130-nm technology, the value for default width and default spacing is 200 nm each and e is 400 nm, yielding a new spacing of 600 nm. However, other values for e are possible, if required.

According to the invention, sets of nets are classified in four types of nets according to their coupling characteristics.

One set of nets is classified as a victim set, which contains nets that are classified victims to one or more coupling issues. One set of nets is classified as an aggressor set, which contains nets that are classified aggressors of one or more coupling issues. One set of nets is classified as a victim-aggressor set, which contains nets that are classified victims and aggressors of one or more coupling issues. One set of nets is classified as a default net, which contain nets which are insensitive to coupling issues. As well known in the art, a net is a logical connection between a signal source and one of more elements receiving the signal. Such nets are implemented as wires in an electronic circuit such as an integrated circuit or a printed circuit board or the like.

Specific distance rules are applied to the different sets of nets which take into account the coupling issues between the different sets of nets.

For implementation of the set of nets in a layout of the electronic circuit, wire types V, A, VA, D are assigned to a specific set of nets. A default wire type D is assigned to the default net, a victim wire type is assigned to the victim nets, an aggressor wire type A is assigned to the aggressor nets, and a victim-aggressor wire type VA is assigned to the victim-aggressor nets. Spacing between proximate wires is chosen depending on their specific wire types. The assigned wire types V, A, VA, D are used by the router program.

Thus, a first distance rule between a first wire and a second wire is applied, which second wire is proximate to the first wire unless:

-   -   the first wire is a victim wire V and the second wire is an         aggressor wire A or a victim-aggressor wire VA, or     -   the first wire is an aggressor wire A and the second wire is a         victim-aggressor wire VA, or     -   the first wire is a victim-aggressor wire VA and the second wire         is a victim wire V or an aggressor wire A or a victim-aggressor         wire VA,         where for these cases a second distance rule is applied.

The table in FIG. 3 exemplifies a first preferred embodiment of the invention. All wire types V, A, AV, D typically are of equal width. This embodiment is appropriate if the router program supports not only spacing based on wire widths, such as the router program known under the name Bonnroute by the International Business and Machines Corporation, for example.

In this example, according to the first distance rule a minimum space d is chosen as a first spacing s1 and with the second distance rule an extra space e is added to the first spacing s1, with s1=d, yielding a second spacing s2, with s2=d+e. Normally, e is a positive number e>0.

As can be seen in the table, the spacing between the default wire type D and all other wire types V, A, VA is equal and preferably the default space d which is usually the minimum space required by the technology used for the fabrication of the electronic device.

The spacing between a victim wire V and a default wire can be d, whereas the spacing between a victim wire V and an aggressor wire A as well as a victim aggressor wire VA has to be larger with d+e.

The spacing between an aggressor wire A and a default wire D as well as an aggressor wire A can be d, whereas the spacing between the aggressor wire A and a victim wire V as well as a victim-aggressor wire VA has to be larger with d+e.

The spacing between a victim-aggressor wire VA and a default wire D can be d, whereas to all other wire types the spacing has to be larger with d+e.

For such router programs which only support spacing based on wire widths, all wire types V, A, AV, D differ in their respective widths, wherein the widths are representative for each specific wire type V, A, AV, D. For example, such a router program is known under the name of Nanoroute by Cadence. Thus, the different wire types can be emulated by using slight differences in wire widths to represent the different wire types V, A, AV, D.

Let w_default represent a default width, s_default represent a default spacing, r represent the resolution of the router program, and assume that the resolution is much smaller than the default width w_default, w_default>>r.

Suppose W(x) is the width of a wire x, and S(x) is the spacing requirement for the wire x. Widths W(x) and spacing requirements S(x) for default wires D, victim wires V, aggressor wires A, and victim-aggressor wires VA can be defined as follows:

-   W(D)=w_default -   W(V)=w_default+2r -   W(A)=w_default+4r -   W(VA)=w_default+6r and -   S(D)=s_default -   S(V)=s_default−2r -   S(A)=s_default−4r -   S(VA)=s_default−6r

As can be seen, the widths W(x) increase from default wire D to victim wire V to aggressor wire A to victim-aggressor wire VA types, wherein the widths increase by an even-numbered multiple of the router resolution r. Preferably, the values for width and spacing are chosen to maintain the original wire pitch, i.e. w_default+s_default and w_default+s_default+e, respectively (FIG. 3). After the routing has been done, preferably for extraction but at least for mask generation, the wire widths should be reset to their original values w_default.

In contrast to the widths W(x), the spacing requirement S(x) decreases from default D to victim V to aggressor A to victim-aggressor wire VA types, wherein the spacing requirement S(x) decreases by an even-numbered multiple of the router resolution r.

A table can be generated similar to the table in FIG. 3 for the first embodiment, as is depicted by the table in FIG. 4.

Again, a first distance rule between a first wire and a second proximate wire is applied, unless

-   -   the first wire is a victim wire V and the second wire is an         aggressor wire A or a victim-aggressor wire VA, or     -   the first wire is an aggressor wire A and the second wire is a         victim-aggressor wire VA, or     -   the first wire is a victim-aggressor wire VA and the second wire         is a victim wire V or an aggressor wire A or a victim-aggressor         wire VA,         where for these cases a second distance rule is applied.

With the first distance rule a wire spacing s3 is applied, which is decreasing in units of the router resolution, starting form the default spacing s_default between two proximate default wires D. With the second distance rule an additional spacing e is added to the first wire spacing s3.

With the first wire a default wire D, the spacing to a proximate victim wire is s_default−r, the spacing to a proximate aggressor wire A is s_default−2r and to a proximate victim-aggressor wire VA is s_default−3r.

If the first wire is a victim wire V and the proximate wire is a default wire D, the spacing is s_default−r, with the proximate wire being a victim wire V, the spacing is s_default−2r, with the proximate wire an aggressor wire A, the spacing is s_default−3r+e, and with the proximate wire a victim-aggressor wire VA, the spacing is s_default−4r+e.

If the first wire is an aggressor wire A and the proximate wire is a default wire D, the spacing is s_default−2r, with the proximate wire a victim wire V, the spacing is s_default−3r+e, with the proximate wire an aggressor wire A, the spacing is s_default−4r, with the proximate wire a victim-aggressor wire VA, the spacing is s_default−5r+e.

If the first wire is a victim-aggressor wire VA and the proximate wire is a default wire D, the spacing is s_default−3r, with the proximate wire being a victim wire V, the spacing is s_default−4r+e, with the proximate wire an aggressor wire A, the spacing is s_default−5r+e, and with the proximate wire a victim-aggressor wire VA, the spacing is s_default−6r+e.

The approaches described in the embodiments can be modified to include additional classes of victim and aggressor nets and/or different wire widths.

The matrices of both tables in FIGS. 3 and 4, respectively, can be adapted to save additional wiring resources. Another improvement, additionally or alternatively, can be to add a weighing function to timing critical nets to avoid detours in important signals.

The IC design is characterized by the steps of

-   -   defining sets of nets of different kinds, especially default         nets, victim nets, aggressor nets, and victim-aggressor nets,     -   perform global routing of the electronic circuit, for each net         yielding an area which is a small subset of the entire chip         area, where local routing can be performed,     -   run a coupling analysis, in order to verify or falsify the         coupling characteristics of the nets,     -   assign wire types V, A, AV, D to the kinds of nets,     -   perform local routing, in order to actually embed the wires and         thus determine their location,     -   run a coupling analysis based on the local routing results,     -   assign wire types V, A, AV, D to the kinds of nets,     -   rip-up and reroute possible new wire types V, A, AV, D, found in         the coupling analysis, and allowing rip-up of others,     -   repeat routing and assigning steps if necessary,     -   reset wire widths to original widths if necessary,     -   return from routing.

FIG. 5 shows a block diagram of an example design flow 500. Design flow 500 may vary depending on the type of integrated circuit (IC) being designed. For example, a design flow 500 for building an application specific IC (ASIC) may differ from a design flow 500 for designing a standard component. Design structure 520 is preferably an input to a design process 510 and may come from an IP provider, a core developer, or other design company or may be generated by the operator of the design flow, or from other sources. Design structure 520 comprises a circuit in the form of schematics or HDL, a hardware-description language (e.g., Verilog, VHDL, C, etc.). Design structure 520 may be contained on one or more machine readable medium. For example, design structure 520 may be a text file or a graphical representation of the circuit. Design process 510 preferably synthesizes (or translates) the circuit into a netlist 580, where netlist 580 is, for example, a list of wires, transistors, logic gates, control circuits, I/O, models, etc. that describes the connections to other elements and circuits in an integrated circuit design and recorded on at least one of machine readable medium. This may be an iterative process in which netlist 580 is resynthesized one or more times depending on design specifications and parameters for the circuit.

Design process 510 may include using a variety of inputs; for example, inputs from library elements 530 which may house a set of commonly used elements, circuits, and devices, including models, layouts, and symbolic representations, for a given manufacturing technology (e.g., different technology nodes, 32 nm, 45 nm, 50 nm, etc.), design specifications 540, characterization data 550, verification data 560, design rules 570, and test data files 585 (which may include test patterns and other testing information). Design process 510 may further include, for example, standard circuit design processes such as timing analysis, verification, design rule checking, place and route operations, etc. One of ordinary skill in the art of integrated circuit design can appreciate the extent of possible electronic design automation tools and applications used in design process 510 without deviating from the scope and spirit of the invention. The design structure of the invention is not limited to any specific design flow.

Ultimately, design process 510 preferably translates the circuit, along with the rest of the integrated circuit design (if applicable), into a final design structure 590 (e.g., information stored in a GDS storage medium). Final design structure 590 may comprise information such as, for example, test data files, design content files, manufacturing data, layout parameters, wires, levels of metal, vias, shapes, test data, data for routing through the manufacturing line, and any other data required by a semiconductor manufacturer to produce the circuit. Final design structure 590 may then proceed to a stage 595 where, for example, final design structure 590: proceeds to tape-out, is released to manufacturing, is sent to another design house or is sent back to the customer.

The invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements. In an embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc.

Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer-readable medium can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

A computer processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.

While a particular embodiment has been shown and described, various modifications of the present invention will be apparent to those skilled in the art. 

1. A hardware description language (HDL) design structure tangibly embodied in a non-transitory computer readable medium accessible by a computer for at least one of at least one of designing, manufacturing, and testing an integrated circuit, and computer processing said HDL design structure to yield a graphical representation of a constant wire pitch routing for each of a plurality of sets of nets, the HDL design structure comprising: said sets of nets representing wires classified by at least one of a plurality of wire types according to coupling characteristics between each of said plurality wire types, said plurality of wire types including: a default set wire type having a width equal to a default width; a victim set wire type having a width equal to said default width plus a twofold value of a router resolution; an aggressor set wire type having a width equal to said default width plus a fourfold value of said router resolution; and a victim-aggressor set wire type having a width equal to said default width plus a six-fold value of said router resolution; where spacing between pairs of proximate wire types of said plurality of wire types being assigned to said sets of nets based on distance rules defined as: a default spacing assigned between proximate default set wire types; said default spacing less a value of said router resolution assigned between said default set wire type proximate said victim set wire type; said default spacing less a twofold value of said router resolution assigned between proximate victim set wire types, and said default set wire type proximate said aggressor set wire type; said default spacing less a threefold value of said router resolution assigned between said default set wire type proximate said victim-aggressor set wire type; said default spacing less said threefold value of said router resolution plus an additional spacing value assigned between said victim set wire type proximate said aggressor set wire type; said default spacing less a fourfold value of said router resolution assigned between two proximate aggressor set wire types; said default spacing less said fourfold value of said router resolution plus said additional spacing value assigned between said victim set wire type proximate said victim-aggressor set wire type; said default spacing less a five-fold value of said router resolution plus said additional spacing value assigned between said aggressor set wire type proximate said victim-aggressor set wire type; and said default spacing less a six-fold value of said router resolution plus said additional spacing value assigned between two proximate victim-aggressor set wire types.
 2. The HDL design structure according to claim 1, where spacing between pairs of proximate wire types of said plurality of wire types is increased to avoid coupling.
 3. The HDL design structure according to claim 1, where said additional spacing value reduces coupling between at least two of said aggressor set wire type, said victim set wire type, and said victim-aggressor set wire type.
 4. The HDL design structure according to claim 1, said constant wire pitch routing yields constant wire pitches of the plurality of wire types for routing.
 5. The HDL design structure according to claim 1, further comprising: the wire widths incrementally increasing from said default set wire types, to said victim set wire types, to said aggressor set wire types, to said victim-aggressor set wire types.
 6. The HDL design structure according to claim 1, further comprising: the spacing requirement incrementally decreasing from said default set wire types, to said victim set wire types, to said aggressor set wire types, to said victim-aggressor set wire types.
 7. The HDL design structure according to claim 1, further comprising: a weighing function applied to at least one timing critical net of said sets of nets.
 8. The HDL design structure according to claim 1, wherein said design structure synthesizes said sets of nets into a netlist, which describes an electronic circuit recorded on said non-transitory machine readable medium.
 9. The HDL design structure according to claim 1, wherein said design structure includes at least one item selected from the group consisting of test data files, characterization data, verification data, and design specifications.
 10. The HDL design structure of claim 1, wherein the design structure resides on said non-transitory machine readable medium as a data format used for the exchange of layout data of integrated circuits. 